Homogeneous Replication
The following section describes how Replicate handles replication between an Google Cloud SQL for MySQL source and an Google Cloud SQL for MySQL target (i.e. homogeneous replication).
-
In homogeneous replication, the source data first passes through the Qlik Replicate data type and is therefore subject to any limitations of that type.
For information on Replicate data types and their limitations (where relevant), see Replicate data types.
For information on which Replicate data types the source data passes through when replicating from Google Cloud SQL for MySQL, see the Google Cloud SQL for MySQL to Qlik Replicate data types mapping table described earlier.
- When replicating a TIMESTAMP column, the time is converted to UTC on the target.
Data types
When replicating to an Google Cloud SQL for MySQL target endpoint, the data types will be identical with the following exceptions:
Google Cloud SQL for MySQL source data types | Google Cloud SQL for MySQL target data types |
---|---|
JSON | LONGTEXT |
When using data types from other database engines, the data type on the target will be the corresponding MySQL data type. For more information on using non-native data types, refer to the MySQL online Help.
Collation
When replicating from one Google Cloud SQL for MySQL endpoint to another, table and column collations will be replicated to the target. Collatable data types are indicated by an asterisk (*) in Table 11–3 above.
To support collation replication, the DBA must ensure that the collations defined for the source Google Cloud SQL for MySQL database are the same as those defined for the target Google Cloud SQL for MySQL database.
Non-nullable columns and Primary/Unique index names
Non-nullable columns and Primary/Unique Index names are preserved during homogeneous replication.